Skip to content

Conversation

@dhower-qc
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@AFOliveira AFOliveira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you did not add the CSRs that this extension comprehends, should we have an issue to track that?

Other than that LGTM

Comment on lines 47 to 51
implies:
- if: S
then:
name: Ssctr
version: "1.0.0"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this statement from the spec need to be accommodated here, and similarly in the "Ssctr" definition below?

Smctr and Ssctr depend on both the implementation of S-mode and the Sscsrind extension.

...or maybe we just need a "requires" field here?

requires: [ S, Sscsrind ]

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"M" is required here, too, I believe.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, we need the 'requires' line you propose. Given that, the condition in the implies line isn't needed -- S must be implemented if Smctr is.

For the "M" requirement: you would think so ;) But, if that's the case, there is no need for Ssctr at all. Now, what you do with a system that has S but no M is a question I can't answer...

@ThinkOpenly
Copy link
Collaborator

I think you did not add the CSRs that this extension comprehends, should we have an issue to track that?

How should we define the "Entry Registers" from Chapter 3 of the extension spec? Maybe they'll come when "Sscsrind" is defined, since access to the registers seems indirect through "siselect/sireg"?

@dhower-qc
Copy link
Collaborator Author

I think you did not add the CSRs that this extension comprehends, should we have an issue to track that?

How should we define the "Entry Registers" from Chapter 3 of the extension spec? Maybe they'll come when "Sscsrind" is defined, since access to the registers seems indirect through "siselect/sireg"?

Yes, I'll add an issue for both Sscdrind and the CSRs of Smctr/Ssctr.

@ThinkOpenly
Copy link
Collaborator

Adding a reference to #512 here, since we got a duplicate PR for it (#573).

This PR also fixes #512.

@dhower-qc dhower-qc added the data entry Add missing data to database label Mar 28, 2025
@dhower-qc
Copy link
Collaborator Author

@dbrash, see comments above

@dhower-qc
Copy link
Collaborator Author

If we adopt #598, we can tag the non-normative part of description to mark it as "non-ratified"

* Zeroes all CTR Entry Registers, for all DEPTH values
* Reset to Zero the optional CTR cycle counter where implemented
** `ctrdata.CC` and `ctrdata.CC` bit fields.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dbrash : this is the same field mentioned twice?

@dbrash
Copy link
Contributor

dbrash commented Apr 17, 2025 via email

Copy link
Collaborator

@ThinkOpenly ThinkOpenly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this just needs a rebase. Paths have changed.

@ThinkOpenly
Copy link
Collaborator

The changes in this PR were copied to #1238, which has now been merged. Closing this PR.

auto-merge was automatically disabled November 12, 2025 22:00

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

data entry Add missing data to database

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants